Unlocking a device by performing gestures on an unlock image

ABSTRACT

A device with a touch-sensitive display may be unlocked via gestures performed on the touch-sensitive display. The device is unlocked if contact with the display corresponds to a predefined gesture for unlocking the device. The device displays one or more unlock images with respect to which the predefined gesture is to be performed in order to unlock the device. The performance of the predefined gesture with respect to the unlock image may include moving the unlock image to a predefined location and/or moving the unlock image along a predefined path. The device may also display visual cues of the predefined gesture on the touch screen to remind a user of the gesture.

RELATED APPLICATIONS

This application is a continuation of U.S. patent application Ser. No.13/204,572 filed Aug. 5, 2011, now U.S. Pat. No. 8,286,103, which is acontinuation of U.S. patent application Ser. No. 12/477,075, filed Jun.2, 2009, now U.S. Pat. No. 8,046,721, which is a continuation of U.S.patent application Ser. No. 11/322,549, filed Dec. 23, 2005, now U.S.Pat. No. 7,657,849, which application are incorporated by referenceherein in their entirety.

This application is related to U.S. patent application Ser. No.11/322,550, titled “Indication of Progress Towards Satisfaction of aUser Input Condition,” filed Dec. 23, 2005, which application isincorporated by reference herein in its entirety.

TECHNICAL FIELD

The disclosed embodiments relate generally to user interfaces thatemploy touch-sensitive displays, and more particularly, to the unlockingof user interfaces on portable electronic devices.

BACKGROUND

Touch-sensitive displays (also known as “touch screens” or“touchscreens”) are well known in the art. Touch screens are used inmany electronic devices to display graphics and text, and to provide auser interface through which a user may interact with the devices. Atouch screen detects and responds to contact on the touch screen. Adevice may display one or more soft keys, menus, and otheruser-interface objects on the touch screen. A user may interact with thedevice by contacting the touch screen at locations corresponding to theuser-interface objects with which she wishes to interact.

Touch screens are becoming more popular for use as displays and as userinput devices on portable devices, such as mobile telephones andpersonal digital assistants (PDAs). One problem associated with usingtouch screens on portable devices is the unintentional activation ordeactivation of functions due to unintentional contact with the touchscreen. Thus, portable devices, touch screens on such devices, and/orapplications running on such devices may be locked upon satisfaction ofpredefined lock conditions, such as upon entering an active call, aftera predetermined time of idleness has elapsed, or upon manual locking bya user.

Devices with touch screens and/or applications running on such devicesmay be unlocked by any of several well-known unlocking procedures, suchas pressing a predefined set of buttons (simultaneously or sequentially)or entering a code or password. These unlock procedures, however, havedrawbacks. The button combinations may be hard to perform. Creating,memorizing, and recalling passwords, codes, and the like can be quiteburdensome. These drawbacks may reduce the ease of use of the unlockingprocess and, as a consequence, the ease of use of the device in general.

Accordingly, there is a need for more efficient, user-friendlyprocedures for unlocking such devices, touch screens, and/orapplications. More generally, there is a need for more efficient,user-friendly procedures for transitioning such devices, touch screens,and/or applications between user interface states (e.g., from a userinterface state for a first application to a user interface state for asecond application, between user interface states in the sameapplication, or between locked and unlocked states). In addition, thereis a need for sensory feedback to the user regarding progress towardssatisfaction of a user input condition that is required for thetransition to occur.

SUMMARY

In some embodiments, a method of controlling an electronic device with atouch-sensitive display includes: detecting contact with thetouch-sensitive display while the device is in a user-interface lockstate; moving an image corresponding to a user-interface unlock state ofthe device in accordance with the contact; transitioning the device tothe user-interface unlock state if the detected contact corresponds to apredefined gesture; and maintaining the device in the user-interfacelock state if the detected contact does not correspond to the predefinedgesture.

In some embodiments, a method of controlling a device with atouch-sensitive display includes: displaying an image on thetouch-sensitive display while the device is in a user-interface lockstate; detecting contact with the touch-sensitive display; transitioningthe device to a user-interface unlock state if the detected contactcorresponds to moving the image to a predefined location on thetouch-sensitive display; and maintaining the device in theuser-interface lock state if the detected contact does not correspond tomoving the image to the predefined location.

In some embodiments, a method of controlling a device with atouch-sensitive display includes: displaying an image on thetouch-sensitive display while the device is in a user-interface lockstate; detecting contact with the touch-sensitive display; andtransitioning the device to a user-interface unlock state if thedetected contact corresponds to moving the image on the touch-sensitivedisplay according to a predefined path on the touch-sensitive display;and maintaining the device in the user-interface lock state if thedetected contact does not correspond to moving the image according tothe predefined path.

In some embodiments, a method of controlling a device with atouch-sensitive display includes: displaying first and second images onthe touch-sensitive display while the device is in a user-interface lockstate; detecting contact with the touch-sensitive display; transitioningthe device to a first active state corresponding to the first image ifthe detected contact corresponds to a predefined gesture with respect tothe first image; and transitioning the device to a second active statedistinct from the first active state if the detected contact correspondsto a predefined gesture with respect to the second image.

The aforementioned methods may be performed by a portable electronicdevice having a touch-sensitive display with a graphical user interface(GUI), one or more processors, memory and one or more modules, programsor sets of instructions stored in the memory for performing thesemethods. In some embodiments, the portable electronic device provides aplurality of functions, including wireless communication.

Instructions for performing the aforementioned methods may be includedin a computer program product configured for execution by one or moreprocessors. In some embodiments, the executable computer program productincludes a computer readable storage medium (e.g., one or more magneticdisk storage devices, flash memory devices, or other non-volatile solidstate memory devices) and an executable computer program mechanismembedded therein.

BRIEF DESCRIPTION OF THE DRAWINGS

For a better understanding of the aforementioned embodiments of theinvention as well as additional embodiments thereof, reference should bemade to the Description of Embodiments below, in conjunction with thefollowing drawings in which like reference numerals refer tocorresponding parts throughout the figures.

FIG. 1 is a block diagram illustrating a portable electronic device,according to some embodiments of the invention.

FIG. 2 is a flow diagram illustrating a process for transitioning adevice to a user-interface unlock state, according to some embodimentsof the invention.

FIG. 3 is a flow diagram illustrating a process for transitioning adevice to a user-interface unlock state, according to some embodimentsof the invention.

FIGS. 4A-4B illustrate the GUI display of a device in a user-interfacelock state, according to some embodiments of the invention.

FIGS. 5A-5D illustrate the GUI display of a device at various points ofthe performance of an unlock action gesture, according to someembodiments of the invention.

FIG. 6 is a flow diagram illustrating a process for indicating progresstowards satisfaction of a user input condition according to someembodiments of the invention.

FIGS. 7A-7D illustrate the GUI display of a device that is transitioningthe optical intensity of user-interface objects, according to someembodiments of the invention.

FIGS. 8A-8C are graphs illustrating optical intensity as a function ofthe completion of the user input condition, according to someembodiments of the invention.

FIG. 9 is a flow diagram illustrating a process for transitioning adevice to a user interface active state, according to some embodimentsof the invention.

FIG. 10 illustrates the GUI of a device in a user-interface lock statethat displays a plurality of unlock images, according to someembodiments of the invention.

FIGS. 11A-11F illustrate the GUI display of a device at various pointsin the performance of an unlock action gesture, according to someembodiments of the invention.

DESCRIPTION OF EMBODIMENTS

Reference will now be made in detail to embodiments, examples of whichare illustrated in the accompanying drawings. In the following detaileddescription, numerous specific details are set forth in order to providea thorough understanding of the present invention. However, it will beapparent to one of ordinary skill in the art that the present inventionmay be practiced without these specific details. In other instances,well-known methods, procedures, components, and circuits have not beendescribed in detail so as not to unnecessarily obscure aspects of theembodiments.

FIG. 1 illustrates a portable electronic device, according to someembodiments of the invention. The device 100 includes a memory 102, amemory controller 104, one or more processing units (CPU's) 106, aperipherals interface 108, RF circuitry 112, audio circuitry 114, aspeaker 116, a microphone 118, an input/output (I/O) subsystem 120, atouch screen 126, other input or control devices 128, and an externalport 148. These components communicate over the one or morecommunication buses or signal lines 110. The device 100 can be anyportable electronic device, including but not limited to a handheldcomputer, a tablet computer, a mobile phone, a media player, a personaldigital assistant (PDA), or the like, including a combination of two ormore of these items. It should be appreciated that the device 100 isonly one example of a portable electronic device 100, and that thedevice 100 may have more or fewer components than shown, or a differentconfiguration of components. The various components shown in FIG. 1 maybe implemented in hardware, software or a combination of both hardwareand software, including one or more signal processing and/or applicationspecific integrated circuits.

The memory 102 may include high speed random access memory and may alsoinclude non-volatile memory, such as one or more magnetic disk storagedevices, flash memory devices, or other non-volatile solid state memorydevices. In some embodiments, the memory 102 may further include storageremotely located from the one or more processors 106, for instancenetwork attached storage accessed via the RF circuitry 112 or externalport 148 and a communications network (not shown) such as the Internet,intranet(s), Local Area Networks (LANs), Wide Local Area Networks(WLANs), Storage Area Networks (SANs) and the like, or any suitablecombination thereof. Access to the memory 102 by other components of thedevice 100, such as the CPU 106 and the peripherals interface 108, maybe controlled by the memory controller 104.

The peripherals interface 108 couples the input and output peripheralsof the device to the CPU 106 and the memory 102. The one or moreprocessors 106 run various software programs and/or sets of instructionsstored in the memory 102 to perform various functions for the device 100and to process data.

In some embodiments, the peripherals interface 108, the CPU 106, and thememory controller 104 may be implemented on a single chip, such as achip 111. In some other embodiments, they may be implemented on separatechips.

The RF (radio frequency) circuitry 112 receives and sendselectromagnetic waves. The RF circuitry 112 converts electrical signalsto/from electromagnetic waves and communicates with communicationsnetworks and other communications devices via the electromagnetic waves.The RF circuitry 112 may include well-known circuitry for performingthese functions, including but not limited to an antenna system, an RFtransceiver, one or more amplifiers, a tuner, one or more oscillators, adigital signal processor, a CODEC chipset, a subscriber identity module(SIM) card, memory, and so forth. The RF circuitry 112 may communicatewith the networks, such as the Internet, also referred to as the WorldWide Web (WWW), an Intranet and/or a wireless network, such as acellular telephone network, a wireless local area network (LAN) and/or ametropolitan area network (MAN), and other devices by wirelesscommunication. The wireless communication may use any of a plurality ofcommunications standards, protocols and technologies, including but notlimited to Global System for Mobile Communications (GSM), Enhanced DataGSM Environment (EDGE), wideband code division multiple access (W-CDMA),code division multiple access (CDMA), time division multiple access(TDMA), Bluetooth, Wireless Fidelity (Wi-Fi) (e.g., IEEE 802.11a, IEEE802.11b, IEEE 802.11g and/or IEEE 802.11n), voice over Internet Protocol(VoIP), Wi-MAX, a protocol for email, instant messaging, and/or ShortMessage Service (SMS)), or any other suitable communication protocol,including communication protocols not yet developed as of the filingdate of this document.

The audio circuitry 114, the speaker 116, and the microphone 118 providean audio interface between a user and the device 100. The audiocircuitry 114 receives audio data from the peripherals interface 108,converts the audio data to an electrical signal, and transmits theelectrical signal to the speaker 116. The speaker converts theelectrical signal to human-audible sound waves. The audio circuitry 114also receives electrical signals converted by the microphone 116 fromsound waves. The audio circuitry 114 converts the electrical signal toaudio data and transmits the audio data to the peripherals interface 108for processing. Audio data may be may be retrieved from and/ortransmitted to the memory 102 and/or the RF circuitry 112 by theperipherals interface 108. In some embodiments, the audio circuitry 114also includes a headset jack (not shown). The headset jack provides aninterface between the audio circuitry 114 and removable audioinput/output peripherals, such as output-only headphones or a headsetwith both output (headphone for one or both ears) and input(microphone).

The I/O subsystem 120 provides the interface between input/outputperipherals on the device 100, such as the touch screen 126 and otherinput/control devices 128, and the peripherals interface 108. The I/Osubsystem 120 includes a touch-screen controller 122 and one or moreinput controllers 124 for other input or control devices. The one ormore input controllers 124 receive/send electrical signals from/to otherinput or control devices 128. The other input/control devices 128 mayinclude physical buttons (e.g., push buttons, rocker buttons, etc.),dials, slider switches, sticks, and so forth.

The touch screen 126 provides both an output interface and an inputinterface between the device and a user. The touch-screen controller 122receives/sends electrical signals from/to the touch screen 126. Thetouch screen 126 displays visual output to the user. The visual outputmay include text, graphics, video, and any combination thereof. Some orall of the visual output may correspond to user-interface objects,further details of which are described below.

The touch screen 126 also accepts input from the user based on hapticand/or tactile contact. The touch screen 126 forms a touch-sensitivesurface that accepts user input. The touch screen 126 and the touchscreen controller 122 (along with any associated modules and/or sets ofinstructions in the memory 102) detects contact (and any movement orbreak of the contact) on the touch screen 126 and converts the detectedcontact into interaction with user-interface objects, such as one ormore soft keys, that are displayed on the touch screen. In an exemplaryembodiment, a point of contact between the touch screen 126 and the usercorresponds to one or more digits of the user. The touch screen 126 mayuse LCD (liquid crystal display) technology, or LPD (light emittingpolymer display) technology, although other display technologies may beused in other embodiments. The touch screen 126 and touch screencontroller 122 may detect contact and any movement or break thereofusing any of a plurality of touch sensitivity technologies, includingbut not limited to capacitive, resistive, infrared, and surface acousticwave technologies, as well as other proximity sensor arrays or otherelements for determining one or more points of contact with the touchscreen 126. The touch-sensitive display may be analogous to themulti-touch sensitive tablets described in the following U.S. Pat. Nos.6,323,846 (Westerman et al.), 6,570,557 (Westerman et al.), and/or6,677,932 (Westerman), and/or U.S. Patent Publication 2002/0015024A1,each of which is hereby incorporated by reference. However, the touchscreen 126 displays visual output from the portable device, whereastouch sensitive tablets do not provide visual output. The touch screen126 may have a resolution in excess of 100 dpi. In an exemplaryembodiment, the touch screen 126 may have a resolution of approximately168 dpi. The user may make contact with the touch screen 126 using anysuitable object or appendage, such as a stylus, finger, and so forth.

In some embodiments, in addition to the touch screen, the device 100 mayinclude a touchpad (not shown) for activating or deactivating particularfunctions. In some embodiments, the touchpad is a touch-sensitive areaof the device that, unlike the touch screen, does not display visualoutput. The touchpad may be a touch-sensitive surface that is separatefrom the touch screen 126 or an extension of the touch-sensitive surfaceformed by the touch screen 126.

The device 100 also includes a power system 130 for powering the variouscomponents. The power system 130 may include a power management system,one or more power sources (e.g., battery, alternating current (AC)), arecharging system, a power failure detection circuit, a power converteror inverter, a power status indicator (e.g., a light-emitting diode(LED)) and any other components associated with the generation,management and distribution of power in portable devices.

In some embodiments, the software components include an operating system132, a communication module (or set of instructions) 134, acontact/motion module (or set of instructions) 138, a graphics module(or set of instructions) 140, a user interface state module (or set ofinstructions) 144, and one or more applications (or set of instructions)146.

The operating system 132 (e.g., Darwin, RTXC, LINUX, UNIX, OS X,WINDOWS, or an embedded operating system such as VxWorks) includesvarious software components and/or drivers for controlling and managinggeneral system tasks (e.g., memory management, storage device control,power management, etc.) and facilitates communication between varioushardware and software components.

The communication module 134 facilitates communication with otherdevices over one or more external ports 148 and also includes varioussoftware components for handling data received by the RF circuitry 112and/or the external port 148. The external port 148 (e.g., UniversalSerial Bus (USB), FIREWIRE, etc.) is adapted for coupling directly toother devices or indirectly over a network (e.g., the Internet, wirelessLAN, etc.).

The contact/motion module 138 detects contact with the touch screen 126,in conjunction with the touch-screen controller 122. The contact/motionmodule 138 includes various software components for performing variousoperations related to detection of contact with the touch screen 122,such as determining if contact has occurred, determining if there ismovement of the contact and tracking the movement across the touchscreen, and determining if the contact has been broken (i.e., if thecontact has ceased). Determining movement of the point of contact mayinclude determining speed (magnitude), velocity (magnitude anddirection), and/or an acceleration (including magnitude and/ordirection) of the point of contact. In some embodiments, thecontact/motion module 126 and the touch screen controller 122 alsodetects contact on the touchpad.

The graphics module 140 includes various known software components forrendering and displaying graphics on the touch screen 126. Note that theterm “graphics” includes any object that can be displayed to a user,including without limitation text, web pages, icons (such asuser-interface objects including soft keys), digital images, videos,animations and the like.

In some embodiments, the graphics module 140 includes an opticalintensity module 142. The optical intensity module 142 controls theoptical intensity of graphical objects, such as user-interface objects,displayed on the touch screen 126. Controlling the optical intensity mayinclude increasing or decreasing the optical intensity of a graphicalobject. In some embodiments, the increase or decrease may followpredefined functions.

The user interface state module 144 controls the user interface state ofthe device 100. The user interface state module 144 may include a lockmodule 150 and an unlock module 152. The lock module detectssatisfaction of any of one or more conditions to transition the device100 to a user-interface lock state and to transition the device 100 tothe lock state. The unlock module detects satisfaction of any of one ormore conditions to transition the device to a user-interface unlockstate and to transition the device 100 to the unlock state. Furtherdetails regarding the user interface states are described below.

The one or more applications 130 can include any applications installedon the device 100, including without limitation, a browser, addressbook, contact list, email, instant messaging, word processing, keyboardemulation, widgets, JAVA-enabled applications, encryption, digitalrights management, voice recognition, voice replication, locationdetermination capability (such as that provided by the globalpositioning system (GPS)), a music player (which plays back recordedmusic stored in one or more files, such as MP3 or AAC files), etc.

In some embodiments, the device 100 may include the functionality of anMP3 player, such as an iPod (trademark of Apple Computer, Inc.). Thedevice 100 may, therefore, include a 36-pin connector that is compatiblewith the iPod. In some embodiments, the device 100 may include one ormore optional optical sensors (not shown), such as CMOS or CCD imagesensors, for use in imaging applications.

In some embodiments, the device 100 is a device where operation of apredefined set of functions on the device is performed exclusivelythrough the touch screen 126 and, if included on the device 100, thetouchpad. By using the touch screen and touchpad as the primaryinput/control device for operation of the device 100, the number ofphysical input/control devices (such as push buttons, dials, and thelike) on the device 100 may be reduced. In one embodiment, the device100 includes the touch screen 126, the touchpad, a push button forpowering the device on/off and locking the device, a volume adjustmentrocker button and a slider switch for toggling ringer profiles. The pushbutton may be used to turn the power on/off on the device by depressingthe button and holding the button in the depressed state for apredefined time interval, or may be used to lock the device bydepressing the button and releasing the button before the predefinedtime interval has elapsed. In an alternative embodiment, the device 100also may accept verbal input for activation or deactivation of somefunctions through the microphone 118.

The predefined set of functions that are performed exclusively throughthe touch screen and the touchpad include navigation between userinterfaces. In some embodiments, the touchpad, when touched by the user,navigates the device 100 to a main, home, or root menu from any userinterface that may be displayed on the device 100. In such embodiments,the touchpad may be referred to as a “menu button.” In some otherembodiments, the menu button may be a physical push button or otherphysical input/control device instead of a touchpad.

User Interface States

The device 100 may have a plurality of user interface states. A userinterface state is a state in which the device 100 responds in apredefined manner to user input. In some embodiments, the plurality ofuser interface states includes a user-interface lock state and auser-interface unlock state. In some embodiments, the plurality of userinterface states includes states for a plurality of applications.

In the user-interface lock state (hereinafter the “lock state”), thedevice 100 is powered on and operational but ignores most, if not all,user input. That is, the device 100 takes no action in response to userinput and/or the device 100 is prevented from performing a predefinedset of operations in response to the user input. The predefined set ofoperations may include navigation between user interfaces and activationor deactivation of a predefined set of functions. The lock state may beused to prevent unintentional or unauthorized use of the device 100 oractivation or deactivation of functions on the device 100. When thedevice 100 is in the lock state, the device 100 may be said to belocked. In some embodiments, the device 100 in the lock state mayrespond to a limited set of user inputs, including input thatcorresponds to an attempt to transition the device 100 to theuser-interface unlock state or input that corresponds to powering thedevice 100 off. In other words, the locked device 100 responds to userinput corresponding to attempts to transition the device 100 to theuser-interface unlock state or powering the device 100 off, but does notrespond to user input corresponding to attempts to navigate between userinterfaces. It should be appreciated that even if the device 100 ignoresa user input, the device 100 may still provide sensory feedback (such asvisual, audio, or vibration feedback) to the user upon detection of theinput to indicate that the input will be ignored.

In embodiments where the device 100 includes the touch screen 126, whilethe device 100 is locked, a predefined set of operations, such asnavigation between user interfaces, is prevented from being performed inresponse to contact on the touch screen 126 when the device 100 islocked. In other words, when the contact is being ignored by the lockeddevice 100, the touch screen may be said to be locked. A locked device100, however, may still respond to a limited class of contact on thetouch screen 126. The limited class includes contact that is determinedby the device 100 to correspond to an attempt to transition the device100 to the user-interface unlock state.

In the user-interface unlock state (hereinafter the “unlock state”), thedevice 100 is in its normal operating state, detecting and responding touser input corresponding to interaction with the user interface. Adevice 100 that is in the unlock state may be described as an unlockeddevice 100. An unlocked device 100 detects and responds to user inputfor navigating between user interfaces, entry of data and activation ordeactivation of functions. In embodiments where the device 100 includesthe touch screen 126, the unlocked device 100 detects and responds tocontact corresponding to navigation between user interfaces, entry ofdata and activation or deactivation of functions through the touchscreen 126.

Unlocking a Device Via Gestures

FIG. 2 is a flow diagram illustrating a process 200 for transitioning adevice to a user-interface unlock state, according to some embodimentsof the invention. As used herein, transitioning from one state toanother refers to the process of going from one state to another. Theprocess may be, as perceived by the user, instantaneous,near-instantaneous, gradual or at any suitable rate. The progression ofthe process may be controlled automatically by the device, such as thedevice 100 (FIG. 1), independent of the user, once the process isactivated; or it may be controlled by the user. While the process flow200 described below includes a number of operations that appear to occurin a specific order, it should be apparent that these processes mayinclude more or fewer operations, which may be executed serially or inparallel (e.g., using parallel processors or a multi-threadingenvironment).

A device is set to the lock state (202). The device may be set (that is,transition completely to the lock state from any other state) to thelocked state upon satisfaction of any of one or more lock conditions.The lock conditions may include events such as the elapsing of apredefined time of inactivity, entry into an active call, or powering onthe device. The lock conditions may also include user intervention,namely the user locking the device by a predefined user input. In someembodiments, the user may be allowed to specify the events that serve aslock conditions. For example, the user may configure the device totransition to the lock state upon the elapsing of a predefined time ofinactivity but not upon powering on the device.

In some embodiments, the locked device displays on the touch screen oneor more visual cues of an unlock action that the user may perform tounlock the device (204). The visual cue(s) provide hints or reminders ofthe unlock action to the user. The visual cues may be textual, graphicalor any combination thereof. In some embodiments, the visual cues aredisplayed upon particular events occurring while the device is locked.The particular events that trigger display of the visual cues mayinclude an incoming call, incoming message, or some other event that mayrequire the user's attention. In some embodiments, the visual cues mayalso be displayed upon particular user inputs, such as the userinteracting with the menu button, the user making contact with thelocked touch screen and/or the user interacting with any otherinput/control device. The locked device, when not displaying the visualcues, may power down the touch screen (which helps to conserve power) ordisplay other objects on the touch screen, such as a screen saver orinformation that may be of interest to the user (e.g., battery chargeremaining, date and time, network strength, etc.).

The unlock action includes contact with the touch screen. In someembodiments, the unlock action is a predefined gesture performed on thetouch screen. As used herein, a gesture is a motion of theobject/appendage making contact with the touch screen. For example, thepredefined gesture may include a contact of the touch screen on the leftedge (to initialize the gesture), a horizontal movement of the point ofcontact to the opposite edge while maintaining continuous contact withthe touch screen, and a breaking of the contact at the opposite edge (tocomplete the gesture).

While the touch screen is locked, the user may initiate contact with thetouch screen, i.e., touch the touch screen (206). For convenience ofexplanation, contact on the touch screen in the process 200 and in otherembodiments described below will be described as performed by the userusing at least one hand using one or more fingers. However, it should beappreciated that the contact may be made using any suitable object orappendage, such as a stylus, finger, etc. The contact may include one ormore taps on the touch screen, maintaining continuous contact with thetouch screen, movement of the point of contact while maintainingcontinuous contact, a breaking of the contact, or any combinationthereof.

The device detects the contact on the touch screen (208). If the contactdoes not correspond to an attempt to perform the unlock action, or ifthe contact corresponds to a failed or aborted attempt by the user toperform the unlock action (210—no), then the device remains locked(212). For example, if the unlock action is a horizontal movement of thepoint of contact across the touch screen while maintaining continuouscontact with the touch screen, and the detected contact is a series ofrandom taps on the touch screen, then the device will remain lockedbecause the contact does not correspond to the unlock action.

If the contact corresponds to a successful performance of the unlockaction, i.e., the user performed the unlock action successfully(210—yes), the device transitions to the unlock state (214). Forexample, if the unlock action is a horizontal movement of the point ofcontact across the touch screen while maintaining continuous contactwith the touch screen, and the detected contact is the horizontalmovement with the continuous contact, then the device transitions to theunlock state.

In some embodiments, the device begins the process of transitioning tothe unlock state upon detection of any contact on the touch screen andaborts the transition as soon as the device determines that the contactdoes not correspond to an unlock action or is a failed/aborted unlockaction. For example, if the unlock action is a predefined gesture, thedevice may begin the process of transitioning to the unlock state assoon as it detects the initial contact of the gesture and continues theprogression of the transition as the gesture is performed. If the useraborts the gesture before it is completed, the device aborts thetransition and remains in the lock state. If the gesture is completed,the device completes the transition to the unlock state and becomesunlocked. As another example, if the unlock action is a horizontalmovement of the point of contact across the touch screen whilemaintaining continuous contact with the touch screen, and the user tapsthe touch screen once, the device begins the process of the statetransition as soon as it detects the tap but also aborts the processsoon after because it realizes that the tap is just a tap and does notcorrespond to the unlock action.

While the device is unlocked, the device may display on the touch screenuser-interface objects corresponding to one or more functions of thedevice and/or information that may be of interest to the user. Theuser-interface objects are objects that make up the user interface ofthe device and may include, without limitation, text, images, icons,soft keys (or “virtual buttons”), pull-down menus, radio buttons, checkboxes, selectable lists, and so forth. The displayed user-interfaceobjects may include non-interactive objects that convey information orcontribute to the look and feel of the user interface, interactiveobjects with which the user may interact, or any combination thereof.The user may interact with the user-interface objects by making contactwith the touch screen at one or more touch screen locationscorresponding to the interactive objects with which she wishes tointeract. The device detects the contact and responds to the detectedcontact by performing the operation(s) corresponding to the interactionwith the interactive object(s).

While the device is locked, the user may still make contact on the touchscreen. However, the locked device is prevented from performing apredefined set of actions in response to any detected contact until thedevice is unlocked. The prevented predefined set of action may includenavigating between user interfaces and entry of data by the user.

While the device is locked, the device may display one or more visualcues of the unlock action, as described above. In some embodiments, thedevice may also display, along with the visual cues, an unlock image.The unlock image is a graphical, interactive user-interface object withwhich the user interacts in order to unlock the device. In other words,the unlock action is performed with respect to the unlock image. In someembodiments, performing the unlock action with respect to the imageincludes dragging the unlock image in a predefined manner, which movesthe unlock image across the touch screen. In some embodiments, if theunlock action is not completed, the GUI display can show reverseprogress towards the locked state by gradually returning the unlockimage to its position in the locked state

In some embodiments, in addition to visual feedback, the electronicdevice supplies non-visual feedback to indicate progress towardscompletion of the unlock action. In some embodiments, in addition tovisual feedback, the electronic device supplies non-visual feedback toindicate completion of the unlock action. The additional feedback mayinclude audible feedback (e.g., sound(s)) or physical feedback (e.g.,vibration(s)).

FIG. 3 is a flow diagram illustrating a process 300 for transitioning adevice to a user-interface unlock state using an unlock image, accordingto some embodiments of the invention. The process 300 is similar to theprocess 200 (FIG. 2) with the addition of an unlock image that isdisplayed with the visual cues. The unlock action in the process 300 isperformed with respect to the unlock image, i.e., the unlock actionincludes interaction with the unlock image. While the process flow 300described below includes a number of operations that appear to occur ina specific order, it should be apparent that these processes can includemore or fewer operations, which can be executed serially or in parallel(e.g., using parallel processors or a multi-threading environment).

The device is locked upon satisfaction of a lock condition (302),similar to the operation 202 (FIG. 2). An unlock image and visual cuesof the unlock action using the unlock image are displayed (304). Theoperation 304 is the same as the operation 204 (FIG. 2), except that inthe operation 304 an unlock image is displayed in addition to the visualcues.

As described above, the unlock action includes interaction with theunlock image. In some embodiments, the unlock action includes the userperforming a predefined gesture with respect to the unlock image. Insome embodiments, the gesture includes dragging the unlock image to alocation on the touch screen that meets one or more predefined unlockcriteria. In other words, the user makes contact with the touch screenat a location corresponding to the unlock image and then performs thepredefined gesture while maintaining continuous contact with the touchscreen, dragging the image to the location that meets the predefinedunlock criteria. In some embodiments, the unlock action is completed bybreaking the contact with the touch screen (thus releasing the unlockimage) upon completion of the predefined gesture.

A location meeting one or more predefined unlock criteria is simply alocation on the touch screen that is predefined as a location to whichthe unlock image is to be dragged in order to unlock the device. Thelocation(s) may be defined narrowly or broadly and may be one or moreparticular locations on the touch screen, one or more regions on thetouch screen, or any combination thereof. For example, the location maybe defined as a particular marked location, areas at each of the fourcorners of the touch screen, or a quadrant of the touch screen, etc.

In some embodiments, the interaction includes dragging the unlock imageto a predefined location on the touch screen. For example, the unlockaction may include dragging the unlock image from one corner of thetouch screen to another corner of the touch screen. As another example,the unlock action may include dragging the unlock image from one edge ofthe touch screen to the opposite edge. The emphasis here is on the finaldestination of the unlock image (and of the finger). Thus, the user candrag the unlock image from its initial location along any desired path.As long as the unlock image reaches the predefined location and isreleased at that location, the device is unlocked. It should beappreciated that the predefined location may be, as described above,defined narrowly or broadly and may be one or more particular locationson the touch screen, one or more regions on the touch screen, or anycombination thereof.

In some other embodiments, the unlock action includes dragging theunlock image along a predefined path. For example, the unlock action mayinclude dragging the unlock image clockwise along the perimeter of thetouch screen (the path being the perimeter of the touch screen), fromone of the corners and back. As another example, the unlock action mayinclude dragging the unlock image from one edge of the touch screen tothe opposite edge in a linear path. The emphasis here is on the pathalong which the unlock image (and the finger) moves. Because of theemphasis on the path, the final location to which the unlock image is tobe moved may be defined broadly. For example, the unlock action may beto drag the unlock image from its initial location, along the predefinedpath, to any spot within a predefined region on the touch screen. Thepredefined path may include one or more straight lines or lines withtwists and turns.

The user makes contact with the touch screen (306), similar to theoperation 206 (FIG. 2). The device detects the contact with the touchscreen (308), similar to the operation 208 (FIG. 2). If the contact doesnot correspond to successful performance of the unlock action withrespect to the image (310—no), the device remains locked. If the contactdoes correspond to successful performance of the unlock action withrespect to the image (310—yes), the device is unlocked (314).

FIGS. 4A-4B illustrate the GUI display of a device in a user-interfacelock state, according to some embodiments of the invention. In FIG. 4A,device 400 includes a touch screen 408 and a menu button 410. The device400 is locked and the touch screen 408 is displaying an unlock image 402and visual cues. The visual cues shown include a channel 404 indicatingthe path of the gesture/movement along which the unlock image 402 is tobe dragged, similar to a groove along which a slider switch moves; andone or more arrows 406 indicating the direction of the gesture/movement.The end of the channel 404 (in FIGS. 4A-4B and 5A-5D, the “end” of thechannel is the right end) also serves as a predefined location to whichthe unlock image 402 is to be dragged. The unlock image 402 may alsoinclude an arrow to further remind the user the direction of thegesture/movement. As described above, the visual cues and the unlockimage may be displayed by the device 400 upon an event that may requirethe user's attention (e.g., incoming call or message) or upon userintervention (e.g., the user pressing the menu button 410 while thedevice is locked).

In some embodiments, the arrows 406 and the arrow on the unlock image402 may be animated. For example, the arrow on the unlock image 402 mayappear and disappear in a pulse-like manner and the arrows 406 mayemanate from one end of the channel 406 in sync with the pulsing of thearrow on the unlock image 402. As shown in FIG. 4B, the arrow 406 maymove along the channel 404 and disappear when it moves to the end of thechannel 404.

The visual cues illustrated in FIGS. 4A and 4B remind the user that theunlock action is a predefined gesture that includes a horizontalmovement of the finger (and thus moving the point of contact) along thechannel 404, from the beginning of the channel 404, where the unlockimage is initially located, to the end of the channel 404. It should beappreciated, however, that the visual cues shown in FIGS. 4A-4B aremerely exemplary and that more or fewer visual cues, or alternativevisual cues may be used. The content of the visual cues may be based onthe particulars of the unlock action.

FIGS. 5A-5D illustrate the GUI display of a device at various points ofthe performance of an unlock action gesture, according to someembodiments of the invention. In FIG. 5A, the user, represented by thehand and finger 502 (not drawn to scale), begins the unlock action bytouching the touch screen 408 of device 400 with her finger 502. In someembodiments, the touch screen 408 is initially in sleep mode and/ordark, and the screen 408 displays the unlock image 402 when touched. Theuser touches the touch screen 408 at the location corresponding to theunlock image 402, which is located initially at the left end of thechannel 404. The contact, either overlapping with the unlock image 402or in proximity to the unlock image 402, is detected by the device 400and is determined to be an attempt to unlock the touch screen, based onthe fact that the user 502 is interacting with the unlock image 402.

In FIG. 5B, the user is in the process of performing the gesture bymoving her finger, which is in continuous contact with the touch screen408, in the direction of movement 504. The unlock image 402 is draggedalong the channel 404 as a result of the gesture. The channel 404reminds the user that the unlock gesture is a horizontal motion. In someembodiments, the channel 404 indicates the predefined location (in FIGS.5A-5D, the right end of the channel) to which the user drags the unlockimage 402 to complete the unlock action and/or the predefined path alongwhich the user drags the unlock image 402 to complete the unlock action.

In FIG. 5C, the user has dragged the unlock image 402 to the right endof the channel 404. Once the user releases the unlock image 402 at theright end of the channel 404, the unlock action is complete. Uponcompletion of the unlock gesture, the device unlocks and displays on thetouch screen 408 user-interface objects associated with normal operationof the device 400. FIG. 5D illustrates an example of user-interfaceobjects that may be displayed when the device 400 is unlocked. In FIG.5D, the device 400 displays a menu 506. The menu 506 includesinteractive user-interface objects corresponding to various applicationsor operations. A user may interact with the user-interface objects toactivate an application or perform an operation. It should beappreciated, however, that the device 400, upon being unlocked, maydisplay additional or alternative user-interface objects.

In some embodiments, the unlock image 402 may also be used to indicatefailure of performance of the unlock action. For example, if the userbreaks the contact with the touch screen before the unlock image reachesthe right end of the channel 404, the unlock action has failed. Thedevice 400 may display the unlock image 402 returning to its initialposition on the left end of the channel 404, allowing the user toattempt the unlock action again, if she so chooses. In some embodiments,the device goes back to sleep if no gesture is applied in apredetermined period of time.

In some embodiments, the user may unlock the device 400 by contactingthe touch screen 408 and moving the point of contact horizontally alonga fraction of the channel 404, i.e., the user need not move all the wayto the right end of the channel. In some embodiments, the user mayunlock the device 400 by making contact anywhere on the touch screen 408and moving the point of contact horizontally as if he or she werefollowing the channel 404.

In some embodiments, the lock/unlock feature may apply to specificapplications that are executing on the device 400 as opposed to thedevice 400 as a whole. In some embodiments, an unlock gesturetransitions from one application to another, for example, from atelephone application to a music player or vice versa. The lock/unlockfeature may include a hold or pause feature. In some embodiments, as theuser transitions from a first application and to a second application, auser interface for the second application may fade in (i.e., increase inintensity) and a user interface for the first application may fade out(i.e., decrease in intensity). The fade in and fade out may occursmoothly over a pre-determined time interval, such as 0.2 s, 1 s or 2 s.The pre-determined time interval may be in accordance with the unlockgesture, such as the time it takes the user to perform the gesture.

Indication of Progress Towards Satisfaction of a User Input Condition

FIG. 6 is a flow diagram illustrating a process 600 for indicatingprogress towards satisfaction of a user input condition according tosome embodiments of the invention. While the process flow 600 describedbelow includes a number of operations that appear to occur in a specificorder, it should be apparent that these processes can include more orfewer operations, which can be executed serially or in parallel (e.g.,using parallel processors or a multi-threading environment).

While an electronic device is in a first user-interface state, progressis detected (602) towards satisfaction of a user input condition neededto transition to a second user-interface state. In some embodiments, thefirst user-interface state is for a first application and the seconduser-interface state is for a second application. In some embodiments,the first user-interface state is a lock state and the seconduser-interface state is an unlock state.

While the device is in the first user-interface state, progress isindicated (604) towards satisfaction of the condition by transitioningan optical intensity of one or more user interface objects associatedwith the second user-interface state. The change in optical intensity ofthe user-interface objects provides a user with sensory feedback of theprogress in transitioning between user interface states.

In some embodiments, in addition to visual feedback, the device suppliesnon-visual feedback to indicate progress towards satisfaction of theuser input condition. The additional feedback may include audiblefeedback (e.g., sound(s)) or physical feedback (e.g., vibration(s)).

The device transitions (606) to the second user-interface state if thecondition is satisfied. In some embodiments, in addition to visualfeedback, the device supplies non-visual feedback to indicatesatisfaction of the user input condition. The additional feedback mayinclude audible feedback (e.g., sound(s)) or physical feedback (e.g.,vibration(s)).

The optical intensity of a user-interface object, as used herein, is theobject's degree of visual materialization. The optical intensity may bemeasured along a scale between a predefined minimum and a predefinedmaximum. In some embodiments, the optical intensity may be measuredalong a logarithmic scale. In some embodiments, the optical intensitymay be perceived by users as a transparency effect (or lack thereof)applied to the user-interface object. In some embodiments, the minimumoptical intensity means that the object is not displayed at all (i.e.,the object is not perceptible to the user), and the maximum opticalintensity means that the object is displayed without any transparencyeffect (i.e., the object has completely materialized visually and isperceptible to the user). In some other embodiments, the opticalintensity may be the visual differentiation between the user-interfaceobject and the background, based on color, hue, color saturation,brightness, contrast, transparency, and any combination thereof.

In some embodiments, the optical intensity of the user-interface objectsto be displayed in the second user-interface state is increasedsmoothly. Smoothly may include a transition time that is greater than apre-defined threshold, for example, 0.2 s, 1 s or 2 s. The rate of thetransition of the optical intensity may be any predefined rate.

In some embodiments, the indication of progress towards completion ofthe user input condition is a function of the user's satisfaction of thecondition. For example, for a transition to an unlock state, theindication of progress towards completion is a function of the user'sperformance of an unlock action. For a linear function, the indicationof progress is 10% complete when the unlock action is 10% complete; theindication of progress is 50% complete when the unlock action is 50%complete, and so forth, up to 100% completion of the unlock action, atwhich point the transition to the unlock state occurs. Correspondingly,for a linear function, the transition of the optical intensity from aninitial value to a final value is 10% complete when the unlock action is10% complete; the transition is 50% complete when the unlock action is50% complete, and so forth, up to 100% completion of the unlock action,at which point the optical intensity is at its final value. In someembodiments, the user may perceive the optical intensity transition as afading in of the user-interface objects as the unlock action isperformed. It should be appreciated that the function need not be linearand alternative functions may be used, further details of which aredescribed below, in relation to FIGS. 8A-8C.

If the user input condition includes a predefined gesture then theindication of progress of the gesture may be defined in terms of howmuch of the gesture is completed and how much of the gesture isremaining. For example, if the gesture includes moving the finger fromone edge of the screen to the opposite edge horizontally, then theindication of progress may be defined in terms of the distance betweenthe two edges because the distance remaining objectively measures howmuch further the user has to move her finger to complete the gesture.

If the user input condition includes dragging an image to a predefinedlocation, then the indication of progress may be defined in terms of thedistance between the initial location of the image and the predefinedlocation to which the image is to be dragged in order to complete theinput condition.

If the user input condition includes dragging an image along apredefined path, then the indication of progress may be defined in termsof the length of the predefined path.

FIGS. 7A-7D illustrate the GUI display of a device that is transitioningthe optical intensity of user-interface objects concurrent with atransition from a first user interface state to a second user interfacestate, according to some embodiments of the invention. In FIG. 7A, thedevice 700 is locked and has received an incoming call. The device 700is displaying a prompt 706 to the user, informing the user of theincoming call, on the touch screen 714. The device is also displayingthe unlock image 702 and channel 704 so that the user can unlock thedevice 700 in order to accept or decline the incoming call. The userbegins the unlock action by making contact on the touch screen with herfinger 710 on the unlock image 702.

In FIG. 7B, the user is in the process of dragging the unlock image 702along the channel 704 in the direction of movement 712. As the userdrags the unlock image, a set of virtual buttons 708 appears andincreases in optical intensity. The virtual buttons 708 are shown withdotted outlines to indicate that they are not yet at their final opticalintensity levels. The virtual buttons 708 are associated with the prompt706; the virtual buttons shown in FIG. 7B-7D allow the user to declineor accept the incoming call. However, the user cannot interact with thevirtual buttons 708 until the device is unlocked and the virtual buttonshave reached their final optical intensity. In FIG. 7C, the user dragsthe unlock image 702 further along the channel 704 in the direction ofmovement 712. The virtual buttons 708 have increased further in opticalintensity relative to their optical intensity in FIG. 7B, as illustratedby their different style of dotted outlines. The increases in opticalintensity indicate to the user progress towards completion of the unlockaction.

In FIG. 7D, the user completes the unlock action by dragging the unlockimage to the right end of the channel 704 and releasing the unlock image702. The device 700 transitions to the unlock state. The unlock image702 and the channel 704 disappear from the display and the virtualbuttons 708 are at their final optical intensity levels, as illustratedby their solid outlines. At this point the user may interact with thevirtual buttons 708 and accept or decline the incoming call.

As described above in relation to FIGS. 5A-5D, if the unlock actionfails because the user releases the unlock image prematurely, the unlockimage may return to its initial location. In some embodiments, theoptical intensity of the virtual buttons 708 or other user-interfaceobjects that were increasing in optical intensity as the unlock actionwas performed may, concurrent with the return of the unlock image to itsinitial location, have their optical intensity decreased smoothly, backto their initial levels.

FIGS. 8A-8C are graphs illustrating optical intensity as a function ofthe completion of the user input condition, according to someembodiments of the invention. In FIG. 8A, the optical intensity is alinear function of the completion of the user input condition. At 0%completion, the optical intensity is at an initial value (in this case,the initial value is 0). As the completion percentage increases, theoptical intensity increases linearly with the completion percentage,until it reaches the final value at 100% completion.

In FIG. 8B, the optical intensity is a nonlinear function of thecompletion of the user input condition. At 0% completion, the opticalintensity is at an initial value (in this case, the initial value is 0).As the completion percentage increases, the optical intensity increasesgradually at first, but the increase becomes steeper as the completionpercentage increases, until it reaches the final value at 100%completion.

In FIG. 8C, the optical intensity is another nonlinear function of thecompletion of the user input condition. At 0% completion, the opticalintensity is at an initial value (in this case, the initial value is 0).As the completion percentage increases, the optical intensity increasessteeply at first, but the increase becomes more gradual as thecompletion percentage increases, until it reaches the final value at100% completion. In some embodiments, the optical intensity may increaseaccording to a logarithmic scale.

In some embodiments, the optical intensity may reach its final valueprior to 100% completion of the user input condition (e.g., at 90%completion).

User Interface Active States Corresponding to Events or Applications

FIG. 9 is a flow diagram illustrating a process 900 for transitioning adevice to a user interface active state corresponding to one of aplurality of unlock images, according to some embodiments of theinvention. In some embodiments, the device may have one or more activeapplications running when the device becomes locked. Additionally, whilelocked, the device may continue to receive events, such as incomingcalls, messages, voicemail notifications, and so forth. The device maydisplay multiple unlock images on the touch screen, each unlock imagecorresponding to an active application or incoming event. Performing theunlock action using one of the multiple unlock images unlocks the deviceand displays the application and/or event corresponding to the unlockimage. The user interface active state, as used herein, means that thedevice is unlocked and a corresponding application or event is displayedon the touch screen to the user. While the process flow 900 describedbelow includes a number of operations that appear to occur in a specificorder, it should be apparent that these processes can include more orfewer operations, which can be executed serially or in parallel (e.g.,using parallel processors or a multi-threading environment).

The device is locked upon satisfaction of a predefined lock condition(902). The device may have active applications running when it is lockedand the active applications may continue running while the device islocked. Additionally, while the device is locked, the device may receiveevents, such as incoming calls, messages, and voicemail notifications.

The device displays a plurality of unlock images, each displayed unlockimage corresponding to an active application running or an eventreceived while the device is locked (904). In some embodiments, thedevice also displays visual cues of the unlock action with respect toeach unlock image. The device may display additional unlock images andvisual cues as additional events are received. The user makes contactwith the touch screen (906). The device detects the contact gesture(908). If the detected contact gesture does not correspond to successfulperformance of the unlock action with respect to any one of thedisplayed unlock images (e.g., because the contact is not an attempt toperform the unlock action or the unlock action failed/was aborted)(910—no), the device remains locked (912). If the detected contactgesture does correspond to successful performance of the unlock actionwith respect to one of the displayed unlock images (910—yes), the touchscreen is unlocked and the running application or event corresponding tothe one of the unlock images is displayed on the touch screen (914). Inother words, the device transitions to a first active statecorresponding to the first image if the detected contact corresponds toa predefined gesture with respect to the first image; the devicetransitions to a second active state distinct from the first activestate and corresponding to the second image if the detected contactcorresponds to a predefined gesture with respect to the second image;and so on.

The device becomes unlocked and makes the corresponding event orapplication visible to the user, active, or running in the foreground,as opposed to running in the background, upon performance of the unlockaction with respect to the particular unlock image. The user-interfaceactive state includes the running application or incoming eventcorresponding to the particular unlock image with which the userinteracted being displayed prominently on the touch screen, in additionto the device being unlocked. Thus, unlocking using a first unlock image(if multiple unlock images are displayed) transitions the device to afirst user-interface active state, in which the device is unlocked andthe application/event corresponding to the first unlock image isdisplayed prominently. Unlocking using a second image transitions thedevice to a second user-interface active state, in which the device isunlocked and the application/event corresponding to the second unlockimage is displayed prominently.

In some embodiments, the device may prioritize which unlock images todisplay. The device may display a subset of the corresponding unlockimages on the touch screen at one time. The device may decide whichsubset to display based on one or more predefined criteria. For example,the device may display only unlock images corresponding to the mostrecent events and/or running applications. As another example, thedevice may display only unlock images corresponding to incoming events.

FIG. 10 illustrates the GUI of a device 1000 in a user-interface lockstate that displays a plurality of unlock images, according to someembodiments of the invention. In FIG. 10, the touch screen 1014 of thedevice 1000 is locked. A first unlock image 1002 is displayed withcorresponding visual cues, such as the first channel 1004 and arrow1006. A second unlock image 1008 is displayed with corresponding visualcues, such as the second channel 1010 and arrow 1012. The touch screen1014 may display additional unlock images and visual cues. The firstunlock image 1002 corresponds to a first running application or receivedevent. The second unlock image 1008 corresponds to a second runningapplication or received event. The first and second unlock images andvisual cues are similar to the unlock image and visual cues describedabove, in relation to FIGS. 4A and 4B. The arrows 1006 and 1012 may beanimated to move from one end of the channels 1004 and/or 1010 to theother end, in order to indicate the proper direction of the predefinedgesture or movement of the unlock image.

FIGS. 11A-11F illustrate the GUI display of a device at various pointsin the performance of an unlock action gesture corresponding to one of aplurality of unlock images, according to some embodiments of theinvention. In FIG. 11A, the user makes contact with the touch screen1014 using her finger 1102 (not shown to scale), at the locationcorresponding to the second unlock image 1008. The user performs theunlock action gesture by moving the point of contact, dragging thesecond unlock image 1008. FIG. 11B shows a snapshot of the device 1000during the pendency of the unlock action. The second unlock image 1008is moved along in the channel 1010 in the direction of movement 1104.

FIG. 11C shows the second unlock image 1008 moved to the end of thechannel 1010, where the unlock action with respect to the second unlockimage 1008 will be completed once the user breaks the contact (andreleases the second unlock image 1008). In some embodiments, the unlockaction is completed when the unlock image 1008 is moved to the end ofthe channel 1010, with or without the user breaking contact, and thesecond unlock image 1008 disappears. As shown in FIG. 11D, uponcompletion of the unlock action with respect to the second unlock image1008, the device displays on the touch screen the user-interface objects1106 associated with the application or event corresponding to thesecond unlock image 1008. In FIG. 11D, the event corresponding to thesecond unlock image is an incoming text message event and a prompt forthe user to read it.

The user, instead of performing the unlock action with respect to thesecond unlock image 1108, may instead perform the unlock action gesturewith respect to the first unlock image 1002. In FIG. 11E, the user doesso and performs the unlock action with respect to the first unlock image1002 by dragging the first unlock image, in the direction 1104, to theright end of the channel 1004. Upon completion of the unlock action, thedevice 1000 displays the user-interface objects 1108 associated with theapplication or event corresponding to the first unlock image 1002. InFIG. 11F, the application corresponding to the first unlock image is amusic player application.

In some embodiments, the transition to a user interface active state, asdescribed in FIGS. 9 and 11A-11E, may also include a concurrenttransition in the optical intensity of user-interface objects, similarto that described above in relation to FIGS. 6, 7A-7D, and 8A-8C.Concurrent with the transition to a user interface active state, theuser-interface objects associated with the application or eventcorresponding to the unlock image with which the user interacted tounlock the device increase in intensity. For example, the opticalintensity of the user-interface objects 1106 associated with the textmessage prompt in FIG. 11D may be increased smoothly, as a function ofthe progress towards completion of the unlock action with respect to thesecond unlock image 1008. As another example, the optical intensity ofthe user-interface objects 1108 associated with music player applicationin FIG. 11F may be increased smoothly, as a function of the progresstowards completion of the unlock action with respect to the first unlockimage 1002.

The foregoing description, for purpose of explanation, has beendescribed with reference to specific embodiments. However, theillustrative discussions above are not intended to be exhaustive or tolimit the invention to the precise forms disclosed. Many modificationsand variations are possible in view of the above teachings. Theembodiments were chosen and described in order to best explain theprinciples of the invention and its practical applications, to therebyenable others skilled in the art to best utilize the invention andvarious embodiments with various modifications as are suited to theparticular use contemplated.

What is claimed is:
 1. A method of controlling a device comprising atouch-sensitive display, comprising: receiving an event at the devicewhile the device is in a lock state, the event associated with anapplication on the device; displaying on the touch-sensitive display anunlock interface, the unlock interface including information about thereceived event and further including an unlock image to accessfunctionality associated with the received event, wherein the unlockimage is a graphical, interactive user-interface object; detecting agesture on the unlock image of the unlock interface on thetouch-sensitive display that satisfies a predefined condition; and inresponse to the detected gesture satisfying the predefined condition:transitioning the device to a user-interface unlocked state for theapplication associated with the received event, and displaying anapplication interface for the application associated with the receivedevent.
 2. The method of claim 1, wherein the event comprises an incomingphone call, and wherein the unlocked state displays an applicationinterface for the phone application.
 3. The method of claim 2, whereinthe unlock interface information comprises notification of the incomingphone call.
 4. The method of claim 3, wherein the unlock interfaceinformation comprises an identifier of the incoming phone call.
 5. Themethod of claim 2, wherein the application interface comprises an acceptcall user-interface object.
 6. The method of claim 2, wherein theapplication interface further comprises a decline call user-interfaceobject.
 7. The method of claim 1, wherein information about the receivedevent identifies the type of event.
 8. The method of claim 7, whereinthe type of event is one of one of an incoming phone call, an incomingmessage, an incoming electronic mail, and a voicemail.
 9. Anon-transitory computer readable memory device containing instructionsthat, when executed by a processor of a portable device also having atouch-sensitive display, cause the processor to perform operationscomprising: receiving an event at the device while the device is in afirst lock state, the event associated with an application on thedevice; displaying on the touch-sensitive display an unlock interface,the unlock interface including information about the received event andfurther including an unlock image to access functionality associatedwith the received event, wherein the unlock image is a graphical,interactive user-interface object; detecting a gesture on the unlockimage of the unlock interface on the touch-sensitive display thatsatisfies a predefined condition; and in response to the detectedgesture satisfying the predefined condition: transitioning the device toa user-interface unlocked state for the application associated with thereceived event, and displaying an application interface for theapplication associated with the received event.
 10. The computerreadable memory device of claim 9, wherein the event comprises anincoming phone call, and wherein the unlocked state displays anapplication interface for the phone application.
 11. The computerreadable memory device of claim 10, wherein the unlock interfaceinformation comprises notification of the incoming phone call.
 12. Thecomputer readable memory device of claim 11, wherein the unlockinterface information comprises an identifier of the incoming phonecall.
 13. The computer readable memory device of claim 10, wherein theapplication interface comprises an accept call user-interface object.14. The computer readable memory device of claim 10, wherein theapplication interface comprises a decline call user-interface object.15. The computer readable memory device of claim 9, wherein informationabout the received event identifies the type of event.
 16. The computerreadable memory device of claim 15, wherein the identified type of eventis one of one of: an incoming phone call, an incoming message, anincoming electronic mail, and a voicemail.
 17. A portable device,comprising: a touch-sensitive display; at least one processor incommunication with the touch-sensitive display; and at least one memoryin communication with the processor, the memory comprising instructionsthat when executed by the processor cause the processor to performoperations comprising, receiving an event at the device while the deviceis in a first lock state, the event associated with an application onthe device; displaying on the touch-sensitive display an unlockinterface, the unlock interface including information about the receivedevent and further including an unlock image to access functionalityassociated with the received event, wherein the unlock image is agraphical, interactive user-interface object; and detecting a gesture onthe unlock image of the unlock interface on the touch-sensitive displaythat satisfies a predefined condition; and in response to the detectedgesture satisfying the predefined condition: transitioning the device toa user-interface unlocked state for the application associated with thereceived event, and displaying an application interface for theapplication associated with the received event.
 18. The device of claim17, wherein the event comprises an incoming phone call, and wherein theunlocked state displays an application interface for the phoneapplication.
 19. The device of claim 18, wherein the unlock interfaceinformation comprises notification of the incoming phone call.
 20. Thedevice of claim 19, wherein the unlock interface information comprisesan identification of the incoming phone call.
 21. The device of claim18, wherein the application interface comprises an accept calluser-interface object.
 22. The device of claim 18, wherein theapplication interface further comprises a decline call user-interfaceobject.
 23. The device of claim 17, wherein information about thereceived event identifies the type of event.
 24. The device of claim 23,wherein the identified type of event is one of one of: an incoming phonecall, an incoming message, an incoming electronic mail, and a voicemail.25. The method of claim 1, wherein the unlock image provides visualfeedback to indicate progress towards completion of the unlock gesture.26. The method of claim 1, wherein the gesture includes continuouscontact with the touch-sensitive display that moves the unlock imagefrom a first region to a second region on the touch-sensitive display.27. The computer readable memory device of claim 9, wherein the unlockimage provides visual feedback to indicate progress towards completionof the unlock gesture.
 28. The computer readable memory device of claim9, wherein the gesture includes continuous contact with thetouch-sensitive display that moves the unlock image from a first regionto a second region on the touch-sensitive display.
 29. The portabledevice of claim 17, wherein the unlock image provides visual feedback toindicate progress towards completion of the unlock gesture.
 30. Theportable device of claim 17, wherein the gesture includes continuouscontact with the touch-sensitive display that moves the unlock imagefrom a first region to a second region on the touch-sensitive display.